ISO-19139 Metadata
-
Metadata Information
-
-
Metadata language: eng
-
Metadata character set: utf8
-
Last update: 2017-06-22
-
Metadata constraints:
-
-
Security constraints:
-
-
Classification system: None.
-
Metadata contact:
-
-
Role: pointOfContact
-
Organization's name: National Atlas of the United States
-
Contact's position: Point of Contact
-
Contact information:
-
-
Phone:
-
-
Voice: 1-888-ASK-USGS (1-888-275-8747)
-
Address:
-
-
Delivery point: 12201 Sunrise Valley Drive
-
City: Reston
-
Administrative area: VA
-
Postal code: 20192
-
Country: US
-
e-mail address: atlasmail@usgs.gov
-
Scope of the data described by the metadata: dataset
-
Scope name: dataset
-
Name of the metadata standard used: ISO 19139 Geographic Information - Metadata - Implementation Specification
-
Version of the metadata standard: 2007
-
Metadata identifier: 1501015718122r4977206723976242
-
Data Identification Information
-
-
Resource citation:
-
-
Title: Streamflow Gaging Stations
-
Date:
-
-
Presentation format: mapDigital
-
Cited responsible party:
-
-
Role: originator
-
Organization's name: U.S. Geological Survey (USGS) National Atlas of the United States
-
Descriptive keywords:
-
-
Place keywords:
-
-
Keywords: Puerto Rico, District of Columbia, Continental United States, Hawaii, U.S. Virgin Islands, Alaska
-
Descriptive keywords:
-
-
Theme keywords:
-
-
Keywords: Hydrology, Drainage, Stream Gauge, Water, Inland Waters, Stream Gage, Streamflow, Hydrography
-
Abstract: This dataset represents all Streamgage Monitoring Stations from the U.S. Geological Survey, for the United States, Puerto Rico, and the U.S. Virgin Islands, in 2024. Gaging stations, or gages, measure the height (stage) and volume of flow at a point location on a water feature. Gages in this map layer were drawn from the National Water Information System (NWIS) Web Interface and linked to the National Hydrography Dataset Plus Version 2 (NHDPlusV2) flowline feature class. Each Streamgage point contains a link to the USGS Water Data site, which provides daily statistics reported from the station.Data pulled from GeoJSON: Release Rebuild with latest NWIS · internetofwater/ref_gages · GitHubThe GeoJSON file references NHDPlusV2 identifiers and the “reference mainstems” which are governed here:https://github.com/internetofwater/ref_rivers/
-
Purpose: Streamgage Monitoring Stations are used to collect information from bodies of water, including Temperature, Discharge, Gage height, and Specific conductance.
-
Dataset language:eng
-
Dataset character set: utf8
-
Resource maintenance:
-
-
Update frequency: irregular
-
Resource constraints:
-
-
General constraints:
-
-
Limitations of use: None (Public Domain Information)
-
Resource constraints:
-
-
Legal constraints:
-
-
Limitations of use: Although these data have been processed successfully on a computer system at the U.S. Geological Survey, no warranty expressed or implied is made by the U.S. Geological Survey regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. No responsibility is assumed by the U.S. Geological Survey in the use of these data. Distributor assumes no liability for misuse of data.
-
Other constraints: None (Public Domain Information)
-
Resource constraints:
-
-
Legal constraints:
-
-
Access constraints: otherRestrictions
-
Other constraints: Other Constraints
-
Resource constraints:
-
-
Legal constraints:
-
-
Use constraints: otherRestrictions
-
Other constraints: Other Constraints
-
Spatial representation type: vector
-
Processing environment: Esri ArcGIS 10.3.1.4959
-
Resource extent:
-
-
Geographic element:
-
-
Bounding rectangle:
-
-
West longitude: -177.30224418999165
-
East longitude: -53.16761918999995
-
North latitude: 72.45846473414782
-
South latitude: 13.871821406574174
-
Supplemental information: If you are using this dataset as a shapefile, please be aware that it was converted from a Geodatabase. As a result, this shapefile may have attribution and metadata errors resulting from the conversion process. The following are known issues: null values may have been changed to 0s (zeros) or to blank values, numbers (including latitude and longitude) may have been rounded up or down, there may be issues with Unicode character strings, and time cannot be stored in a date field. Field names may have been truncated to no longer than 10 characters or completely changed, lengthy string attributes may have been truncated to 254 characters, and attribute columns may have been deleted. Shapefiles do not support coded domains and subtypes therefore the original file geodatabase attribution and metadata information for coded domains and subtypes could be incorrect or missing in the shapefile version. Please visit the following ESRI website for more information: caution-http://pro.arcgis.com/en/pro-app/tool-reference/appendices/geoprocessing-considerations-for-Shapefile-output.htm
-
Credits: U.S. Geological Survey (USGS), Environmental Protection Agency (EPA)
-
Resource point of contact:
-
-
Role: pointOfContact
-
Organization's name: U.S. Geological Survey (USGS) National Atlas of the United States
-
Contact's position: POC
-
Contact information:
-
-
Phone:
-
-
Voice: 1-888-ASK-USGS (1-888-275-8747)
-
Address:
-
-
Delivery point: 12201 Sunrise Valley Drive
-
City: Reston
-
Administrative area: VA
-
Postal code: 20192
-
Country: US
-
e-mail address: atlasmail@usgs.gov
-
Contact instructions: For questions about this map layer or metadata, please contact the National Atlas using the information above, or through the U.S. Geological Survey contact page at http://www.usgs.gov/ask/. For distribution questions, please see the Distribution Information elsewhere in this metadata.
-
Spatial Representation
-
-
Vector Data
-
-
Geometric objects:
-
-
Object type: point
-
Object count: 20032
-
Data Quality
-
-
Scope of quality information:
-
-
Level of the data:dataset
-
Resource lineage:
-
-
Lineage statement: Data was created from GeoJSON file hosted https://github.com/internetofwater/ref_gages/releases/tag/v0.8.
The GeoJSON file references NHDPlusV2 identifiers and the “reference mainstems” which are governed here: https://github.com/internetofwater/ref_rivers/ It’s probably best to just reference NHDPlusV2 as the key spatial data and link to and this service for the registry of mainstem river IDs that the gages are linked to. https://reference.geoconnex.us/collections/mainstems
-
Process step:
-
-
Description: Made 'Station_NM' attribute column all caps and removed extra spaces. Transferred ESRI metadata to FGDC metadata.
-
Processor:
-
-
Role: processor
-
Organization's name: HIFLD Support Team
-
Process step:
-
-
Description: Calculation of Review The Review attribute provides information about when the gage location was reviewed, or about what entity reviewed the location of the gage during data compilation. It was calculated primarily from the Reviewed attribute in the NHDPlus version 1 and version 2 source data sets.
-
Process source:
-
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2009-01-01T00:00:00
-
Description: Selection of Gages from NHDPlus V1 Stream Gages Gages were obtained from the NHDPlus V1 Gages. If the gage's reach code matched a reach code in the National Atlas Streams 1:1M map layer then the gage was included and snapped to the nearest point on the nearest stream. The reach code of the gage was compared to the reach code of the stream the gage snapped to. If the codes were not identical then the station name for the gage was compared to topographic map stream names to determine if the gage should be moved to a different stream with a matching reach code or if the reach code for the gage should be corrected.
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2010-01-01T00:00:00
-
Description: Selection of Gages from the National Water Information System Web Interface The NHDPlus V1 Gages were from 2004. Additional gages were obtained from NWIS Web to supplement the NHDPlus V1 Gages. Gages were downloaded in February 2010, and gages with daily data in the following categories were selected: > > Parameter code = 00060 - Streamflow, ft3/s > Parameter code = 00065 - Gage height, ft > Parameter code = 00054 - Reservoir storage, acre-ft > Parameter code = 00053 - Surface Area, acres > Parameter code = 00055 - Stream velocity, ft/s > Parameter code = 00059 - Streamflow rate, gal/min > Parameter code = 00062 - Reservoir elevation, ft > Parameter code = 50042 - Discharge, gallons per minute > Parameter code = 50051 - Flow rate, instantaneous, million gallons > per day > Parameter code = 72022 - Reservoir contents, M gal > Parameter code = 99020 - Elevation above NGVD 1929, ft > Parameter code = 99060 - Streamflow, m3/s > Parameter code = 99065 - Gage height, m
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2011-01-01T00:00:00
-
Description: Selection of Additional Gages and Streams Gages from the NWIS Web download were snapped to streams in the National Atlas Streams 1:1M. If the gage couldn't be snapped to a 1:1M stream, it was snapped to the NHDPlus V1 NHDFlowlines, or in Alaska, to the High-Resolution NHDFlowlines. Any gages that could not be snapped to one of these three sources were deleted. To determine if gages were snapped to the correct stream, the station name was compared to stream names from National Atlas Streams 1:1M, NHDPlus V1 NHDFlowline, High-Resolution NHDFlowline, topographic maps, and aerial imagery. The 1:1M gages and streams were edited simultaneously. Gages were used to determine if additional streams should be added to the streams map layer, and streams were used to determine if gages should be added in the gages map layer. Gages were reviewed visually, using topographic maps, aerial imagery, NHDPlus V1 NHDFlowlines, High-Resolution NHDFlowline, and National Atlas Streams 1:1M. Gages were not added to the map layer if adding their corresponding stream was inconsistent with the density of streams in the area, if other gages on similar streams were nearby, if the stream order was lower than other streams in the area, or if the gage was on a canal. At the same time, the stream was added to the National Atlas Streams 1:1M map layer.
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of Reach Code National Atlas Streams 1:1M 2014 has reach codes that were updated to match the reach codes in NHDPlus V2 NHDFlowlines in the 48 conterminous States; High-Resolution NHDFlowlines in Alaska, Puerto Rico, and the U.S. Virgin Islands; and Medium-Resolution NHDFlowlines in Hawaii. All 1:1M gages were checked and, if necessary, their reach codes were updated to match their corresponding stream in National Atlas Streams 1:1M 2014.
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of Lat_1M and Long_1M Latitude and longitude coordinates were calculated for the location of the gage using ArcGIS. These coordinates may be different from the coordinates in NWIS because the streams the gages are on have been generalized and moved for cartographic reasons.
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Integration of Gages with Version 2 of the 1:1M Streams National Atlas Streams 1:1M 2014 (version 2 of the streams map layer) contains minor adjustments along the U.S.-Canada border and in other places where the data were improved or corrected. Gages were checked to verify that they were snapped to the correct stream and were moved if necessary.
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of Region and HUC8 The two-digit region code (Hydrologic Unit Code or HUC) was calculated from the first two digits of the reach code. The eight-digit sub-basin code (Hydrologic Unit Code or HUC) was calculated from the first eight digits of the reach code.
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Combination of NHDPlus V2 Gage Locations and Gage Info The NHDPlus V2 Gage Locations and Gage Info files were downloaded from the NHDPlus website. The Gage Info table was joined to the Gage Locations table and the combined data were exported to a new feature class.
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of the Gage_ID The Gage_ID is the unique identifier for gages in the 1:1M map layer. The starting number is 100,001.
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of State Abbreviation and FIPS codes The gages were intersected with the National Atlas States 1:1M 2014 map layer to transfer the State abbreviations and Federal Information Processing Series (FIPS) codes. The intersected layer was analyzed to determine which gages fell in multiple States. For gages on State boundaries, the State abbreviations and FIPS codes were concatenated with a hyphen to include information from multiple States. Gages outside the boundaries of the States layer were removed.
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of Agency_CD, Site_NO, Station_NM, Site_TP_CD, Lat_NWIS, Long_NWIS Attributes values for Agency_CD, Site_NO, Station_NM, Site_TP_CD, Lat_NWIS, Long_NWIS were determined from the agency_cd, site_no, station_nm, site_tp_cd, dec_lat_va, and dec_long_va values in NWIS Web.
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Selection of Gages from NHDPlus V2 Gages NHDPlus V2 Gages were checked to see if they had matching reach codes in National Atlas Streams 1:1M 2014. If they had a matching reach code and they were not already in the gages map layer, they were snapped to the stream and added. NHDPlus V2 Gages that did not have a matching reach code in the streams were reviewed if their drainage area was greater than 100 square miles. The station name for the gage was checked against topographic maps, imagery, and stream names to determine if the gage should be moved to a different stream, have its reach code changed, and be added to the gages map layer
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of Stream_ID The Stream_ID is the unique identifier of the stream that the gage is snapped to. The value comes from the National Atlas Streams 1:1M 2014 map layer and links the two map layers together. There may be more than one gage sharing the same Stream_ID. No gage has more than one Stream_ID.
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of NWISWeb The URL for the gage's NWIS web page was calculated by concatenating the gage's site number and a generic NWISWeb URL.
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of Source The value for the Source attribute was determined from the data set from which the gage was obtained.
-
Process source:
-
-
Process source:
-
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2014-01-01T00:00:00
-
Description: Calculation of Measure Gages were intersected with National Atlas Streams 1:1M 2014 and each gage was assigned a measure that corresponds to its location on a reach. Measures range from 0 to 100 and record the distance, as a percentage, from the downstream end of a reach. If a reach is composed of more than one stream segment, the measure is based on the length of the entire group of segments that comprise the reach. Measures are used in linear referencing.
-
Process source:
-
-
Process step:
-
-
When the process occurred: 2024-03-21T00:00:00
-
Description: David Blodgett provided the most recent available dataset for Gages, which is still being developed between USGS and EPA.
HIFLD generated a Feature Service based on the GeoJSON file provided by USGS.
https://github.com/internetofwater/ref_gages/releases/tag/v0.8. Additional updates are likely to occur over the next year.
-
Processor:
-
-
Role: originator
-
Individual's name: David Blodgett
-
Organization's name: U.S. Geological Survey
-
Source:
-
-
Data quality report:
-
-
Topological consistency:
-
-
Evaluation method: Stream gage positions were checked against streams in the National Atlas Streams 1:1M 2014 map layer to ensure that each gage has a corresponding 1:1M stream and no gage is associated with more than one stream. Stream_IDs and ReachCodes were compared to Stream_IDs and ReachCodes in the National Atlas Streams 1:1M 2014 map layer to ensure that corresponding gages and streams have identical values. Stream gages downloaded from NWIS Web were compared to aerial imagery and topographic maps to ensure they are located on the correct stream. Attributes were checked for nulls and valid values. Stream gages were checked to ensure that they are within national boundaries and coastlines. Stream gage positions were checked against streams in the National Atlas Streams 1:1M 2014 map layer to ensure that each gage has a corresponding 1:1M stream and no gage is associated with more than one stream. Stream_IDs and ReachCodes were compared to Stream_IDs and ReachCodes in the National Atlas Streams 1:1M 2014 map layer to ensure that corresponding gages and streams have identical values. Stream gages downloaded from NWIS Web were compared to aerial imagery and topographic maps to ensure they are located on the correct stream. Attributes were checked for nulls and valid values. Stream gages were checked to ensure that they are within national boundaries and coastlines.
-
Data quality result:
-
-
Data quality report:
-
-
Conceptual consistency:
-
-
Measure produced by the test: Stream gage positions were checked against streams in the National Atlas Streams 1:1M 2014 map layer to ensure that each gage has a corresponding 1:1M stream and no gage is associated with more than one stream. Stream_IDs and ReachCodes were compared to Stream_IDs and ReachCodes in the National Atlas Streams 1:1M 2014 map layer to ensure that corresponding gages and streams have identical values. Stream gages downloaded from NWIS Web were compared to aerial imagery and topographic maps to ensure they are located on the correct stream. Attributes were checked for nulls and valid values. Stream gages were checked to ensure that they are within national boundaries and coastlines. Stream gage positions were checked against streams in the National Atlas Streams 1:1M 2014 map layer to ensure that each gage has a corresponding 1:1M stream and no gage is associated with more than one stream. Stream_IDs and ReachCodes were compared to Stream_IDs and ReachCodes in the National Atlas Streams 1:1M 2014 map layer to ensure that corresponding gages and streams have identical values. Stream gages downloaded from NWIS Web were compared to aerial imagery and topographic maps to ensure they are located on the correct stream. Attributes were checked for nulls and valid values. Stream gages were checked to ensure that they are within national boundaries and coastlines.
-
Data quality result:
-
-
Data quality report:
-
-
Completeness omission:
-
-
Measure produced by the test: This map layer contains selected stream gages in the United States, Puerto Rico, and the U.S. Virgin Islands. Sites were selected only if they were within the terrestrial and coastal boundaries of the U.S., they had a corresponding stream in the National Atlas Streams 1:1M map layer, they had one of the following site types: > Canal > Ditch > Diversion > Estuary > Lake, Reservoir, Impoundment > Spring > Stream > Tidal Stream > Wetland > and they had daily values in the following list of parameters: > 00060 - Streamflow, ft/s > 00065 - Gage height, ft > 00054 - Reservoir storage, acre-ft > 00053 - Surface Area, acres > 00055 - Stream velocity, ft/s > 00059 - Streamflow rate, gal/min > 00062 - Reservoir elevation, ft > 50042 - Discharge, gallons per minute > 50051 - Flow rate, instantaneous, million gallons per day > 72022 - Reservoir contents, M/gal > 99020 - Elevation above NGVD 1929, ft > 99060 - Streamflow, m/s > 99065 - Gage height, m
-
Data quality result:
-
-
Data quality report:
-
-
Quantitative attribute accuracy:
-
-
Measure produced by the test: The Gage_ID and Site_NO attributes were checked for duplicates and null values. All features have unique values. The values for Site_TP_CD, Lat_NWIS, Long_NWIS, Lat_1M, and Long_1M were checked to ensure that there are no null values and that all values are in the correct domain. Values in the ReachCode field were checked to ensure that there are no null values. They were cross-checked with the Huc8 and Region values, and were checked against the ReachCode for the corresponding stream in the National Atlas Streams 1:1,000,000-scale (1:1M) map layer. Values in the Stream_ID field were checked to ensure that there are no null values. Stream_IDs were also compared to Stream_IDs in the National Atlas Streams 1:1M map layer to ensure that corresponding gages and streams have identical codes. Values in the Region and Huc8 fields were checked to ensure that there are no null values and all values are in the correct domain. Selections by attribute and location were used to ensure the region code matches the region the gage is in. Values in the State and State_FIPS fields were checked to ensure that there are no null values and all values are in the correct domain. All remaining attribute fields were checked to ensure that there are no null values.
-
Data quality result:
-
-
Data quality report:
-
-
Absolute external positional accuracy:
-
-
Measure produced by the test: Most gages had their location reviewed during the creation of the NHDPlus version 1 and version 2 source data and therefore reflect the accuracy of those sources. Gages from NWIS Web had their location reviewed during the creation of this data set. Gages were located on (snapped to) streams in the National Atlas Streams 1:1M 2014 map layer. The streams had been generalized, and in some cases moved as much as 300 meters from nearby transportation features, so gages were relocated along with their corresponding stream.
-
Data quality result:
-
-
Distribution Information
-
-
Distributor:
-
-
Distributor contact:
-
-
Role: distributor
-
Individual's name: Lucinda D. McKay
-
Organization's name: U.S. Geological Survey
-
Contact's position: distributor
-
Contact information:
-
-
Address:
-
-
Country: US
-
e-mail address: nhd@usgs.gov
-
e-mail address: nhdplus-support@epa.gov
-
Distributor format:
-
-
Format name: Vector Digital Data Set (Point)
-
Format version:
-
Distribution order process:
-
-
Terms and fees: None. No fees are applicable for obtaining the data set.
-
Transfer options:
-
-
Online distribution information:
-
-
Online location: https://www.epa.gov/waterdata/get-nhdplus-national-hydrography-dataset-plus-data